-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Addon pko doc #14
base: main
Are you sure you want to change the base?
Addon pko doc #14
Conversation
|
||
## Tenants Onboarding Steps | ||
|
||
Team's can generate the packageImage themselves using the [package operator documentation](https://package-operator.run/docs/guides/packaging-an-application/#build--validate) or Team's can use Managed Tenants Bundles (MTB) facilities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Team's can generate the packageImage themselves using the [package operator documentation](https://package-operator.run/docs/guides/packaging-an-application/#build--validate) or Team's can use Managed Tenants Bundles (MTB) facilities. | |
Teams can generate the packageImage themselves using the [package operator documentation](https://package-operator.run/docs/guides/packaging-an-application/#build--validate) or teams can use Managed Tenants Bundles (MTB) facilities. |
|
||
## Tenants Onboarding Steps | ||
|
||
Team's can generate the packageImage themselves using the [package operator documentation](https://package-operator.run/docs/guides/packaging-an-application/#build--validate) or Team's can use Managed Tenants Bundles (MTB) facilities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Team's can generate the packageImage themselves using the [package operator documentation](https://package-operator.run/docs/guides/packaging-an-application/#build--validate) or Team's can use Managed Tenants Bundles (MTB) facilities. | |
Teams can generate the packageImage themselves using the [package operator documentation](https://package-operator.run/docs/guides/packaging-an-application/#build--validate) or teams can use Managed Tenants Bundles (MTB) facilities. |
|
||
Team's can generate the packageImage themselves using the [package operator documentation](https://package-operator.run/docs/guides/packaging-an-application/#build--validate) or Team's can use Managed Tenants Bundles (MTB) facilities. | ||
|
||
Below are the Steps for generating the packageImage using MTB for reference-addon packageImage : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Below are the Steps for generating the packageImage using MTB for reference-addon packageImage : | |
Below are the Steps for generating the packageImage using MTB for reference-addon packageImage: |
content/en/docs/creating-addons/top-level-operator/addon-package.md
Outdated
Show resolved
Hide resolved
In MTB, a Team just have to create a "package" directory: | ||
https://gitlab.cee.redhat.com/service/managed-tenants-bundles/-/tree/main/addons/reference-addon/package and add the manifests there, alongside the manifests.yaml[PackageManifest] . | ||
|
||
MTB CI will create the packageImage (in addition to the OLM Index Image which are also part of the Team's addon folder https://gitlab.cee.redhat.com/service/managed-tenants-bundles/-/tree/main/addons/reference-addon ) . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MTB CI will create the packageImage (in addition to the OLM Index Image which are also part of the Team's addon folder https://gitlab.cee.redhat.com/service/managed-tenants-bundles/-/tree/main/addons/reference-addon ) . | |
MTB CI will create the packageImage (in addition to the OLM Index Image which is also part of the Team's addon folder https://gitlab.cee.redhat.com/service/managed-tenants-bundles/-/tree/main/addons/reference-addon) . |
content/en/docs/creating-addons/top-level-operator/addon-package.md
Outdated
Show resolved
Hide resolved
Based on review
@garrettthomaskth could you take a look now ? |
|
||
MTB CI will create the packageImage (in addition to the OLM Index Image which is also part of the Team's addon folder https://gitlab.cee.redhat.com/service/managed-tenants-bundles/-/tree/main/addons/reference-addon) . | ||
|
||
The last step for the team is to raise a MR to [managed-tenants repository](https://gitlab.cee.redhat.com/service/managed-tenants/-/blob/main/addons/reference-addon/addonimagesets/stage/reference-addon.v0.10.1.yaml#L24) , adding a new AddonImageSet with those images. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you're using MTB, this step of creating the MT with the AddonImageSet is also automated.
I'd reccomend action using the MTB flow, that will help with documenting the steps.
|
||
MTB CI will create the packageImage (in addition to the OLM Index Image which is also part of the Team's addon folder https://gitlab.cee.redhat.com/service/managed-tenants-bundles/-/tree/main/addons/reference-addon) . | ||
|
||
Then MTB CI raises a MR to [managed-tenants repository](https://gitlab.cee.redhat.com/service/managed-tenants/-/blob/main/addons/reference-addon/addonimagesets/stage/reference-addon.v0.10.1.yaml#L24) , adding a new AddonImageSet with those images. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can write something like, Once the MTB Pr is merged and builds are successful a MR is generated...
No description provided.